Skip to main content

This is a new service – your feedback will help us to improve it.

Tewkesbury Borough Council

Tree preservation zone

There is a problem

  • 435 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Land At Chargrove Lane Up Hatherley Cheltenham Gloucestershire GL51 4XB

reference
A6-384-MIXED
name
Land At Chargrove Lane Up Hatherley Cheltenham Gloucestershire GL51 4XB
tree-preservation-order

undefined

https://tewkesburybc.s3.eu-west-2.amazonaws.com/tpos/TPO384_Land_at_Chargrove_Ln_Shurdington.pdf
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.116045 51.879236,-2.116055 51.879307,-2.116142 51.879426,-2.116286 51.879556,-2.116373 51.879616,-2.116363 51.879640,-2.116057 51.880128,-2.115694 51.880877,-2.116665 51.881197,-2.117415 51.881476,-2.117550 51.881548,-2.117637 51.881577,-2.117887 51.881648,-2.118656 51.881885,-2.118876 51.881570,-2.118934 51.881421,-2.119096 51.881094,-2.119115 51.881088,-2.119268 51.880773,-2.119316 51.880630,-2.119268 51.880547,-2.119239 51.880505,-2.119066 51.880434,-2.118912 51.880392,-2.118671 51.880321,-2.118508 51.880286,-2.118296 51.880221,-2.117469 51.879888,-2.117171 51.879758,-2.116776 51.879610,-2.116862 51.879336,-2.116112 51.879182,-2.116045 51.879236)))
point
POINT (-2.11748 51.880655)
notes
entry-date
2018-10-25
start-date
2018-10-25
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Tewkesbury Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL